|
JIRA 4.4 : MySQL Administrator and Data Truncation Errors
This page last changed on Apr 11, 2011 by dchan.
Hi All, Due to the release of the 3.7 branch requiring an empty database on startup (see here), a lot of our customers have had issues importing their data into the new install due to encoding inconsistencies between their existing databases and the new ones they've created for 3.7.x. Errors that users are seeing are Data Truncation errors that look like:
org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:INSERT INTO jiraaction (ID, issueid, AUTHOR, actiontype, actionlevel, rolelevel, actionbody, CREATED, actionnum) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation: Data too long for column 'actionbody' at row 1)\ at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:375)
I hope this helps and saves you all some installation hiccups. -Michelle |
| Document generated by Confluence on Aug 18, 2011 23:28 |